| Package | hl7.terminology |
| Type | ValueSet |
| Id | Id |
| FHIR Version | R5 |
| Source | http://terminology.hl7.org/https://build.fhir.org/ig/HL7/UTG/ValueSet-v3-ActClassConsent.html |
| Url | http://terminology.hl7.org/ValueSet/v3-ActClassConsent |
| Version | 3.0.0 |
| Status | active |
| Date | 2014-03-26 |
| Name | ActClassConsent |
| Title | ActClassConsent |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | The Consent class represents informed consents and all similar medico-legal transactions between the patient (or his legal guardian) and the provider. Examples are informed consent for surgical procedures, informed consent for clinical trials, advanced beneficiary notice, against medical advice decline from service, release of information agreement, etc. The details of consents vary. Often an institution has a number of different consent forms for various purposes, including reminding the physician about the topics to mention. Such forms also include patient education material. In electronic medical record communication, consents thus are information-generating acts on their own and need to be managed similar to medical activities. Thus, Consent is modeled as a special class of Act. The "signatures" to the consent document are represented electronically through Participation instances to the consent object. Typically an informed consent has Participation.typeCode of "performer", the healthcare provider informing the patient, and "consenter", the patient or legal guardian. Some consent may associate a witness or a notary public (e.g., living wills, advanced directives). In consents where a healthcare provider is not required (e.g. living will), the performer may be the patient himself or a notary public. Some consent has a minimum required delay between the consent and the service, so as to allow the patient to rethink his decisions. This minimum delay can be expressed in the act definition by the ActRelationship.pauseQuantity attribute that delays the service until the pause time has elapsed after the consent has been completed. |
| Copyright | This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html |
No resources found
| CodeSystem | |
v3-ActClass  | ActClass |
Note: links and images are rebased to the (stated) source
Generated Narrative: ValueSet v3-ActClassConsent
Language: en
FHIRhttp://terminology.hl7.org/CodeSystem/v3-ActClass where concept is-a CONS{
"resourceType" : "ValueSet",
"id" : "v3-ActClassConsent",
"language" : "en",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet v3-ActClassConsent</b></p><a name=\"v3-ActClassConsent\"> </a><a name=\"hcv3-ActClassConsent\"> </a><a name=\"v3-ActClassConsent-en-US\"> </a><div style=\"display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%\"><p style=\"margin-bottom: 0px\">Language: en</p></div><ul><li>Include codes from<a href=\"CodeSystem-v3-ActClass.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActClass</code></a> where concept is-a <a href=\"CodeSystem-v3-ActClass.html#v3-ActClass-CONS\">CONS</a></li></ul></div>"
},
"url" : "http://terminology.hl7.org/ValueSet/v3-ActClassConsent",
"identifier" : [
{
"system" : "urn:ietf:rfc:3986",
"value" : "urn:oid:2.16.840.1.113883.1.11.20206"
}
],
"version" : "3.0.0",
"name" : "ActClassConsent",
"title" : "ActClassConsent",
"status" : "active",
"experimental" : false,
"date" : "2014-03-26",
"publisher" : "Health Level Seven International",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://hl7.org"
},
{
"system" : "email",
"value" : "hq@HL7.org"
}
]
}
],
"description" : "The Consent class represents informed consents and all similar medico-legal transactions between the patient (or his legal guardian) and the provider. Examples are informed consent for surgical procedures, informed consent for clinical trials, advanced beneficiary notice, against medical advice decline from service, release of information agreement, etc.\r\n\r\nThe details of consents vary. Often an institution has a number of different consent forms for various purposes, including reminding the physician about the topics to mention. Such forms also include patient education material. In electronic medical record communication, consents thus are information-generating acts on their own and need to be managed similar to medical activities. Thus, Consent is modeled as a special class of Act.\r\n\r\nThe \"signatures\" to the consent document are represented electronically through Participation instances to the consent object. Typically an informed consent has Participation.typeCode of \"performer\", the healthcare provider informing the patient, and \"consenter\", the patient or legal guardian. Some consent may associate a witness or a notary public (e.g., living wills, advanced directives). In consents where a healthcare provider is not required (e.g. living will), the performer may be the patient himself or a notary public.\r\n\r\nSome consent has a minimum required delay between the consent and the service, so as to allow the patient to rethink his decisions. This minimum delay can be expressed in the act definition by the ActRelationship.pauseQuantity attribute that delays the service until the pause time has elapsed after the consent has been completed.",
"immutable" : true,
"copyright" : "This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html",
"compose" : {
"include" : [
{
"system" : "http://terminology.hl7.org/CodeSystem/v3-ActClass",
"filter" : [
{
"property" : "concept",
"op" : "is-a",
"value" : "CONS"
}
]
}
]
}
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.